Systems, methods, and devices for v2x services over wireless wide area networks

ABSTRACT

The present disclosure includes systems and methods that enable V2X communications over a wireless wide area network (WWAN). A registration request is sent to an intelligent transportation system (ITS) function. The registration request is for requesting authorization for a device to host a V2X service in a cellular network. A registration response is received from the ITS function. The registration response is for authorizing the device to host the V2X service in the cellular network. The V2X service is hosted in the cellular network via the ITS function.

RELATED APPLICATIONS

This application is an international filing based on U.S. ProvisionalPatent Application No. 62/222,579, titled V2X IP SERVICES IN LTE/5G,filed Sep. 23, 2015, which is hereby incorporated herein by reference inits entirety.

TECHNICAL FIELD

The present disclosure generally relates to vehicular communicationservices, such as vehicle-to-vehicle (V2V), vehicle-to-pedestrian (V2P),and vehicle-to-infrastructure (V2I), which are sometimes referred toindividually and collectively as vehicle-to-anything or vehicularcommunication (V2X).

BACKGROUND INFORMATION

Wireless mobile communication technology enables communication of mobileuser equipment devices, such as smartphones, tablet computing devices,laptop computers, and the like. Mobile communication technology mayenable connectivity of various types of devices, supporting the“Internet of things.” Vehicles are one example of mobile user equipmentthat may benefit from connectivity over wireless mobile communicationtechnology.

Wireless mobile communication technology uses various standards andprotocols to transmit data between a base station and a wirelesscommunication device. Wireless wide area network (WWAN) communicationsystem standards and protocols can include, for example, the 3rdGeneration Partnership Project (3GPP) long term evolution (LTE), and theIEEE 802.16 standard, which is commonly known to industry groups asworldwide interoperability for microwave access (WiMAX). Wireless localarea network (WLAN) can include, for example, the IEEE 802.11 standard,which is commonly known to industry groups as Wi-Fi. Other WWAN and WLANstandards and protocols are also known.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates one example of an environment in which the presentsystems and methods may be implemented.

FIG. 2 is a block diagram illustrating one example of how the V2Xservices may be incorporated into the inter-PLMN ProSe referencearchitecture.

FIG. 3 is a block diagram illustrating one embodiment of the V2X serviceapplication and the V2X host application in a ProSe environment.

FIG. 4 is a block diagram illustrating one example of a UE connecting toa UE that is enabled to host a V2X service.

FIG. 5 is a block diagram illustrating one example of a UE connecting toan eNB that is enabled to host a V2X service.

FIG. 6 is one example of a message sequence diagram for the describedsystems and methods.

FIG. 7 is another example of a message sequence diagram for thedescribed systems and methods.

FIG. 8 is a flow diagram of a method for V2X communication.

FIG. 9 is a flow diagram of a method for V2X communication.

FIG. 10 is a flow diagram of a method for enabling V2X communication.

FIG. 11 is a flow diagram of a method for enabling V2X communication.

FIG. 12 is a flow diagram of a method for mobility management for V2Xcommunication.

FIG. 13 is a block diagram illustrating electronic device circuitry thatmay be eNB circuitry, UE circuitry, network node circuitry, or someother type of circuitry in accordance with various embodiments.

FIG. 14 is a block diagram illustrating, for one embodiment, examplecomponents of a UE, MS device, or eNB.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.The same reference numbers may be used in different drawings to identifythe same or similar elements. In the following description, for purposesof explanation and not limitation, specific details are set forth suchas particular structures, architectures, interfaces, techniques, etc. inorder to provide a thorough understanding of the various aspects of thedisclosed embodiments. However, it will be apparent to those skilled inthe art having the benefit of the present disclosure that the variousaspects of the embodiments may be practiced in other examples thatdepart from these specific details. In certain instances, descriptionsof well-known devices, circuits, and methods are omitted so as not toobscure the description of the embodiments with unnecessary detail.

In 3GPP radio access networks (RANs) in LTE systems, a base station mayinclude Evolved Universal Terrestrial Radio Access Network (E-UTRAN)Node Bs (also commonly denoted as evolved Node Bs, enhanced Node Bs,eNodeBs, or eNBs) and/or Radio Network Controllers (RNCs) in an E-UTRAN,which communicate with a wireless communication device, known as userequipment (UE). In LTE networks, an E-UTRAN may include a plurality ofeNBs and may communicate with a plurality of UEs. An evolved packet core(EPC) may communicatively couple the E-UTRAN to an external network,such as the internet. LTE networks include radio access technologies(RATs) and core radio network architecture that can provide high datarate, low latency, packet optimization, and improved system capacity andcoverage.

In homogeneous networks, a node, also called a macro node or macro cell,may provide basic wireless coverage to wireless devices in a cell. Thecell may be the area in which the wireless devices can communicate withthe macro node. Heterogeneous networks (HetNets) may be used to handlethe increased traffic loads on the macro nodes due to increased usageand functionality of wireless devices. HetNets may include a layer ofplanned high power macro nodes (macro-eNBs or macro cells) overlaid withlayers of lower power nodes (small cells, small-eNBs, micro-eNBs,pico-eNBs, femto-eNBs, or home eNBs (HeNBs)) that may be deployed in aless well-planned or even entirely uncoordinated manner within thecoverage area (cell) of a macro node. The lower power nodes maygenerally be referred to as “small cells,” small nodes, or low powernodes. HetNets may also include various types of nodes utilizing varyingtypes of RATs, such as LTE eNBs, 3G NodeBs, Wi-Fi APs, and WiMAX basestations.

As used herein, the terms “node” and “cell” are both intended to besynonymous and refer to a wireless transmission point operable tocommunicate with multiple wireless mobile devices, such as a UE, oranother base station. Furthermore, cells or nodes may also be Wi-Fiaccess points (APs), or multi-radio cells with Wi-Fi/cellular oradditional RATs. For example, nodes or cells may include varioustechnologies such that cells operating on different RATs are integratedin one unified HetNet.

Vehicular communication is a relatively new and rapidly emergingresearch and development area opening new market opportunities forwireless communication systems. Vehicular communication can includevehicle-to-vehicle (V2V) (e.g., communication between a vehicle andanother vehicle); vehicle-to-pedestrian (V2P) (e.g., communicationbetween a vehicle and a device carried by an individual, such as apedestrian, cyclist, driver, or passenger); andvehicle-to-infrastructure (V2I) (e.g., communication between a vehicleand a road side unit (RSU), which is a transportation infrastructureentity, for example, an entity transmitting speed notifications), whichare individually and/or collectively referred to as vehicle-to-anything(V2X) communications.

Intelligent Transportation Systems (ITS) enabled by connected vehiclescan improve safety and efficiency in roadways. The range of applicationsfor V2X communication in ITS varies from road safety and vehiculartraffic management to applications enabling infotainment, the vision ofa “connected car,” and “autonomous driving.”

The Wireless Access in Vehicular Environments (WAVE) architecture andstandards has been developed to support ITS safety and non-safetyapplications. WAVE has traditionally relied on Institute of Electricaland Electronics Engineers (IEEE) 802.11p, aka Dedicated Short RangeCommunications (DSRC), to support vehicle to anything (V2X)communications. DSRC/802.11p was specifically designed for vehicularcommunication and utilizes portions of the 5.9 GHz spectrum which havebeen dedicated for ITS.

Many ITS applications require the widespread deployment of DSRC/802.11pinfrastructure to provide meaningful function. For example, many ITSapplications require the deployment of DSRC/802.11p-based Road SideUnits (RSU) (e.g., an entity supporting V2X service). However, therequirement of widespread deployment of infrastructure imposesscalability and deployment cost challenges. Unfortunately, thedeployment of needed DSRC/802.11p infrastructure has been lacking. Thishas led to the consideration of alternative wireless systems. Inparticular, existing cellular systems, such as LTE, are being consideredas an alternative to DSRC/802.11p due to their large scale coverage andefficient spectrum utilization.

The study of direct communication between devices was addressed in the3rd Generation Partnership Project (3GPP) in the area of ProximityServices (ProSe). The current working assumption in the 3GPP standardsis that the communication between the UE and the RSU may be done usingProSe/D2D (i.e., over the PC5 interface) and that the RSU functionalitywill be implemented in the service/application layer in the UE or eNB.Optionally the communication between the UE and the RSU may be done viathe wireless Uu interface (interface between UE and eNodeB). Theprocedures disclosed herein are assuming PC5 interface is used forcommunication between the UE and the RSU, but same procedures can applyin case the Uu interface is used. Given that V2X safety applications andservices provided by RSUs may require delays as low as 1 ms, UEs shouldbe able to discover and get authorization for V2X services from an RSUwithin very low latencies. Such services should also be supportedreliably under high mobility.

However, to date, the main drivers for the existing ProSe architectureand protocols have been public safety (e.g., voice communication betweenemergency responders) and consumer applications (e.g., advertisement,location information, social networks). Unfortunately, existing LTEProSe functionality and protocols are not scalable to efficiently tomeet the requirements of V2X communications in terms of latency andnumber of vehicles supported. Accordingly, improvements are needed. Inparticular, there is a need for efficient procedures to discover a UE oran eNB that is operating as an RSU.

The disclosed systems and methods provide for a registration andauthorization procedure for enabling UEs or eNBs to operate as an RSU.In addition to enabling a UE or an eNB to operate as an RSU, thedisclosed systems and methods enable a UE or an eNB to host V2X safetyIP services, including providing for a V2X service advertisement methodand mobility management protocols for providing seamless connectivity toV2X services.

In some embodiments, the V2X service advertisement method includeshaving a V2X function in the core network provide a list of RSUs andcorresponding services to UEs. Additionally or alternatively, the UEs oreNBs may broadcast V2X service capabilities that enable V2X UEs toidentify RSUs supporting V2X IP services with low overhead and latency.A mobility management protocol for providing seamless connectivity toV2X services is also proposed. Accordingly, the systems and methodsdisclosed herein may enable V2X UEs to discover and maintainconnectivity to V2X services with low overhead and latency.

Therefore, V2X services may be provided over wireless wide area networks(WWANs) (e.g., cellular networks). In some embodiments, V2X serviceswill use the ProSe/device-to-device (D2D) architecture with theenhancement needed to support the transmission of V2X messages. TheseV2X messages may be IP messages and the V2X services may be IP-basedapplications that are carried on the user plane of a PC5 directcommunication interface.

In one example, a UE communicates with a UE or an eNB that is configuredto be a Road Side Unit (RSU) (a vehicle to infrastructure (V2I)scenario, for example). In this example, the UE or eNB that is operatingas an RSU receives safety messages from one UE and relays the safetymessage to another UE. In some cases, this relaying of safety messagesis performed as part of a service provided by an intelligenttransportation system (ITS) server (the relaying may be carried outaccording to the configuration/functionality of the service, forexample).

As used herein, a V2X UE may be a UE that supports ProSe and V2Xenabling features. As used herein, a V2X ProSe function may be V2Xspecific functionality that may be part of the ProSe function or standalone.

Referring now to the figures, FIG. 1 illustrates one example of anenvironment 100 in which the present systems and methods may beimplemented. The environment 100 includes one or more vehicles (e.g.,V2X UEs) 110 that are able to operate as a user equipment (UE) thatsupports both ProSe and V2X communication. As illustrated in FIG. 1, V2XUEs 110B and 110D are connected to an evolved Node B (eNB) 102 via anLTE-Uu interface 120, while V2X UEs 110A and 110C are not be connectedto the eNB 102 (e.g., they may be connected to a different eNB via anLTE-Uu interface 120 or may not be connected to any eNB via an LTE-Uuinterface 120). As illustrated in FIG. 1, V2X UEs 110A-D are eachconnected to a device (e.g., eNB 102 or UE 104) via an LTE-PC5 interface130. For example, V2X UE 110A is connected to the eNB 102 via LTE-PC5interface 130A, V2X UE 110B is connected to the eNB 102 via LTE-PC5interface 130B, V2X UE 110C is connected to the UE 104 via LTE-PC5interface 130C, V2X UE 110D is connected to the UE 104 via LTE-PC5interface 130D, and V2X UE 110A is connected to V2X UE 110B via LTE-PC5interface 130E. In one example, LTE-PC5 interfaces 130 is used for thecontrol plane and the user plane for ProSe Direct Discovery, ProSeDirect Communication, and/or ProSe UE-to-Network Relay.

The environment 100 additionally includes an Intelligent TransportationSystem (ITS) function 106 which provides V2X services. In some cases,the ITS function 106 may be implemented as part of a ProSe function. Inother cases, the ITS function 106 may be implemented as part of a newentity within the cellular network. In yet other cases, the ITS function106 may be external to the cellular network. The ITS function 106 may beimplemented as an ITS server. As used herein, the terms ITS function andITS server are interchangeable. The ITS function 106 may be connected tothe eNB 102 via connection 108. Additionally or alternatively, the ITSfunction 106 may be connected to the UE 104 operating as an RSU. Theenvironment 100 may also include one or more vehicles 112 that either donot support ProSe and/or V2X communication or are not able to operate asa UE.

In one example, the non-V2X UE 112 may turn into the path of V2X UE 110Dcausing a collision between the non-V2X UE 112 and the V2X UE 110D. Itis appreciated that if the non-V2X UE 112 had been able to use V2Xservices and/or V2X communications, such a collision may have beenavoided. Although the V2X UE 110D was not able to avoid a collision withthe non-V2X UE 112, V2X services could be used to help other V2X UEs 110be forewarned or even be rerouted away from the collision.

In one example, the V2X UE 110D that was involved in the collision mayuse a V2X service (e.g., hazard avoidance service, crash notificationservice, traffic rerouting service) that is provided by the ITS function106 and hosted by the UE 104 to indicate that a collision has occurred.The UE 104 may be connected to the ITS function 106 via the LTE-Uu 120connection and the connection 108. As illustrated in FIG. 1, thecommunication between the V2X UE 110D and the UE 104 is a directProSe/D2D connection over the LTE-PC5 interface 130D.

The ITS function 106 may provide relevant notifications of the collisionto nearby V2X UEs 110 via particular V2X services. For example, V2X UE110C receives notification via its LTE-PC5 130C connection with the UE104 and V2X UEs 110A and 110B receive notifications via their respectiveLTE-PC5 interfaces 130 with the eNB 102. In some cases, the V2X UE 110B,which has both an LTE-PC5 interface 130B and an LTE-Uu interface 120,may access V2X services through either the LTE-PC5 interface 130B or theLTE-Uu interface 120. In other cases, the V2X UE 110B, which has both anLTE-PC5 interface 130B and an LTE-Uu interface 120, may access V2Xservices only through the LTE-PC5 interface 130B. For example, the PC5interface 130B may be used for local V2X messaging (e.g., locationspecific, geographically limited, V2X messages). In yet other cases, thePC5 interface 130 may be used primarily for connections between UEs(e.g., V2X UEs 110, UEs 104) and V2X UEs 110A and 110B may access V2Xservices only through the LTE-Uu interface 120.

As is illustrated in FIG. 1, both the eNB 102 and the UE 104 host V2Xservices. For example, both the eNB 102 and the UE 104 act as a RoadSide Unit (RSU) for purposes of hosting V2X services and enabling V2Xcommunication.

FIG. 2 is a block diagram illustrating one example of how the V2Xservices may be incorporated into the inter-PLMN ProSe referencearchitecture 200. A V2X UE 110 includes a ProSe application 212. TheProSe application 212 enables efficient device-to-device (D2D) discoveryand communication. In some cases, the ProSe application 212 managesProSe functionality based on a preconfigured (e.g., PLMN specific) ProSeconfiguration. The ProSe application 212 includes a V2X serviceapplication 250. The V2X service application 250 enables the V2X UE 110to perform V2X communication using ProSe (over the LTE-PC5 interface,for example).

The V2X UE 110 is coupled to the E-UTRAN 216 via an LTE-Uu interface120. The E-UTRAN 216 includes one or more eNBs (not shown). The E-UTRAN216 is connected to the evolved packet core (EPC) 218 via the LTE-S1interface 230. The EPC 218 includes a serving gateway (S-GW) 220, amobility management entity (MME) 222, and a packet gateway (P-GW) 224.The MME 222 is connected to the home subscriber server (HSS) 232 via theLTE-S6a interface 228 and the HSS 232 is connected to the ProSe function240 via the LTE-PC4a interface 236. In one example, the LTE-S6ainterface 228 is used to download ProSe related subscription informationto the MME 222 during an E-UTRAN attach procedure or to inform the MME222 that the subscription information in the HSS 232 has changed. In oneexample, the LTE-PC4a interface 236 is used to provide subscriptioninformation to the ProSe function 240 in order to authorize access forProSe Direct Discovery and ProSe Direct Communication on a per PLMNbasis. In some cases, the LTE-PC4a interface 236 is also used by theProSe function 240 (i.e., EPC-level ProSe Discovery Function) forretrieval of EPC-level ProSe Discovery related subscriber data.

The ProSe function 240 is also connected to the secure user planelocation (SUPL) Location Platform (SLP) 234 via the LTE-PC4b interface238. In one example, the LTE-PC4b interface 238 is used by the ProSefunction 240 (i.e., EPC-level ProSe Discovery Function) in the role ofLCS client to query the SLP defined in the open mobile alliance (OMA) ADSUPL. Using the information from the HSS 232 and the SLP 234, the ProSefunction 240 is able to manage ProSe services. The ProSe function 240 isconnected to the V2X UE 110 via the LTE-PC3 interface 246. In oneexample, the LTE-PC3 interface 240 relies on the EPC 218 user plane fortransport (i.e., an “over IP” reference point). In some cases, theLTE-PC3 interface 246 is used to authorize ProSe Direct Discovery andEPC-level ProSe Discovery requests, and perform allocation of ProSeApplication Codes corresponding to ProSe Application Identities used forProSe Direct Discovery. Additionally or alternatively, the LTE-PC3interface 246 is used to define the authorization policy per PLMN forProSe Direct Discovery (for public safety and non-public safety) andcommunication (for public safety only) between the V2X UE 110 and ProSeFunction 240.

The ProSe function 240 is also connected to a ProSe application server244 via the LTE-PC2 interface 248. In one example, the LTE-PC2 interface248 is used to define the interaction between the ProSe applicationserver 244 and the ProSe functionality provided by the 3GPP EPS via theProSe function 240 (e.g., name translation) for EPC-level ProSediscovery. The ProSe application server 244 is connected with the ProSeapplication 212 via the LTE-PC1 interface 226. In one example, theLTE-PC1 interface 226 is used to define application level signalingrequirements. The ProSe application 212 manages ProSe services based ongeneral (e.g., per PLMN) ProSe configuration. The ProSe application 212may also manage application level signaling based on received signalingrequirements.

As illustrated in FIG. 2, the ProSe function 240 includes a V2X ProSefunction 242 which, in combination with a V2X service application 250within the ProSe application 212, enables the V2X UE 110 to use ProSefor V2X services and V2X communication.

A device 210, which may be another V2X UE (e.g., V2X UE 110), an eNB(e.g., eNB 102), or a UE (e.g., a UE 104), may have a similar ProSearchitecture. In some cases, the device 210 uses a different applicationthan the V2X UE 110. For example, the ProSe application 212 of thedevice 210 includes a V2X host application 214. The V2X host application214 enables the device 210 to host V2X services that are provided by anintelligent transportation system. The V2X host application 214 alsoenables the device 210 to perform the registration and authentication tobecome an RSU and to operate as an RSU using ProSe (over the LTE-PC5interface, for example). In some cases, V2X communication is enabled viaone or more V2X services that are hosted using the V2X host application214.

As illustrated in FIG. 2, the V2X UE 110 is connected to the device 210via an LTE-PC5 interface 130. Although the V2X UE 110 and the device 210are illustrated as being in different public land mobile networks(PLMNs) (e.g., PLMN A, PLMN B), it is understood that the V2X UE 110 andthe device 210 may be in the same PLMN. Although not shown, an LTE-PC6interface is between ProSe functions in different PLMNs (EPC-level ProSeDiscovery) or between the ProSe function in the HPLMN and the ProSefunction in a local PLMN (ProSe Direct Discovery). With ProSe DirectDiscovery this LTE-PC6 interface is used for HPLMN control of ProSeservice authorization. Additionally or alternatively, the LTE-PC6interface is used to authorize ProSe Direct Discovery requests, retrievethe Discovery Filter(s) corresponding to ProSe Application ID name(s),and translate the ProSe application code to the ProSe Application IDname. As is illustrated in FIG. 2, the ProSe architecture may besubstantially similar for both the V2X UE 110 and the device 210. It isalso noted that the LTE-PC5 interface 130 is independent of anyinterface between the V2X UE 110 and the E-UTRAN 216.

FIG. 3 is a block diagram illustrating one embodiment of the V2X serviceapplication 250 and the V2X host application 214 in a ProSe environment300. The V2X UE 110 communicates with the device 210 via the LTE-PC5interface 130. The LTE-PC5 interface 130 may also be referred to as aProSe interface, D2D interface, or direct interface. The V2X UE 110 andthe device 210 each have a communication architecture for communicatingover the LTE-PC5 interface 130. For example, the V2X UE 110 and thedevice 210 each include a physical (PHY) layer 310, a medium accesscontrol (MAC) layer 308, a radio link control (RLC) layer 306, a packetdata convergence protocol (PDCP) layer 304, and an internet protocol(IP) layer 302. Both the V2X UE 110 and the device 210 also include anapplication layer that includes a ProSe application 212.

The ProSe application 212 in the device 210 includes a V2X hostapplication 214, and the ProSe application 212 in the V2X UE 110includes a V2X service application 250. The V2X host application 214 andthe V2X service application 250 communicate over the LTE-PC5 interface130 via the IP layer 302. In some embodiments, the V2X host application214 additionally or alternatively communicates over an LTE-Uu interface120 (e.g., the LTE user plane).

Device 210, which may be a UE (e.g., V2X UE 110), a UE (e.g., UE 104),or an eNB (e.g., eNB 102), may operate as an RSU and host V2Xcommunication via ProSe. The V2X host application 214 enables the device210 to operate as an RSU and host V2X communication, including one ormore V2X services, using ProSe (as part of the ProSe application 212,for example).

V2X UE 110 uses one or more V2X services hosted by the device 210 tocommunicate V2X messages via ProSe. The V2X service application 250enables the V2X UE 110 to engage in V2X communication, including usingone or more V2X services, via ProSe (as part of the ProSe application212, for example).

FIG. 4 is a block diagram illustrating one example 400 of a V2X UE 110connecting to a UE 104 that is enabled to host a V2X service. Asillustrated in FIG. 3, the V2X UE 110 and the UE 104 include acommunication architecture for communicating over the LTE-PC5 interface130. The eNB 102 similarly includes a communication architecture forcommunicating with a UE 104 over the LTE-Uu interface 120. The eNB 102additionally includes a general packet radio service (GPRS) tunnelingprotocol user plane (GTP-U) layer 402, a user datagram protocol (UDP)/IPlayer 404, a layer 2 (L2) layer 406, and a layer 1 (L1) layer 408 forcommunicating with the EPC 218 over the LTE-S1 interface 230.

The EPC 218 includes an MME 222, an S-GW 220, and a P-GW 224. The MME222 includes a NAS security module 410, an idle state mobility handlingmodule 412, and an EPS bearer control module 414. The S-GW 220 includesa mobility anchoring module 416. In some cases, the eNB 102 is coupledto the mobility anchoring module 416 in the S-GW 220. The P-GW 224includes a UE IP address allocation module 418 and a packet filteringmodule 420. The P-GW 224 is connected to the internet 422.

As discussed with respect to FIG. 3, the UE 104 includes a ProSeapplication 212 that includes a V2X host application 214, and the V2X UE110 includes a ProSe application 212 that includes a V2X serviceapplication 250. At least the ProSe application 212 of the UE 104 isconnected to the ProSe function 240. The ProSe function 240 enables theProSe application 212 to perform ProSe and configures the parameters ofhow the ProSe application 212 should operate. Even if the ProSeapplication 212 of the V2X UE 110 is not presently connected to a ProSefunction 240, at some previous time, the ProSe application 212 wouldhave received authorization to use the ProSe application 212 and theconfiguration and parameters for operating the ProSe function 240.

In some cases, the V2X host application 214 performs a registration andauthorization procedure to operate as an RSU and host V2X service. TheV2X host application 214 obtains an internet protocol (IP) address forhosting one or more V2X services. The obtained IP address is allocatedto the V2X host application 214 from the P-GW 224. Using the obtained IPaddress, the V2X host application 214 establishes a connection with theITS function 106 through the P-GW 224. The V2X host application 214establishes a bearer with the ITS function 106, which is maintained viathe EPS bearer control module 414.

The V2X host application 214 sends an authorization request to the ITSfunction 106 to verify that the UE 104 is authorized to provide V2Xservices. Examples of V2X services include hazard notification services,hazard avoidance services, traffic mitigation services, trafficrerouting services, smart cruise control services, pedestrian warningservices, etc. In some cases, the request to register one or more V2Xservices is a request to operate as a road side unit (RSU). Theauthorization request may include the service capabilities and securityinformation of the UE 104. The capabilities sent by the V2X hostapplication 214 may include a list of hosted service identifiers (e.g.,provider service identifier (PSID)) and associated service parameters.

In one example, the ITS function 106 is within the 3GPP domain. Forexample, the ITS function 106 may be part of the V2X ProSe function 242.In another example, the ITS function 106 is a separate server within the3GPP domain. Alternatively, the ITS function 106 is outside of the 3GPPdomain. For example, the ITS function 106 may be accessible via theinternet 422. The IP address of the ITS function 106 may be found by theeNB 102 based on a domain name system (DNS) query using a pre-definedwell known address.

Assuming that the UE 104 is a trusted device, the ITS function 106provides an authorization response to the V2X host application 214confirming that the V2X host application 214 within the UE 104 isauthorized to operate as an RSU (e.g., V2X RSU) and host the requestedV2X service(s).

Having received the authorization from the ITS function 106 to operateas an RSU and host one or more V2X services, the V2X host application214 registers its V2X services with the ITS function 106. The V2X hostapplication 214 sends its hosted service identifiers (e.g., PSID), IPaddress, link layer address (e.g., cell ID), and location information tothe ITS function 106. The ITS function 106 processes the request and mayauthorize one or more V2X services based on the capability list andcredentials provided by the V2X host application 214 (the capabilitylist and credentials of the UE 104, in this case). In some cases, theITS function 106 registers the V2X services and/or the V2X hostapplication 214 with the V2X ProSe function 240.

Additionally or alternatively, the V2X host application 214 registersits V2X services with the V2X ProSe function 240. The V2X hostapplication 214 sends its hosted service identifiers (e.g., PSID), IPaddress, link layer address (e.g., cell ID), and location information tothe ProSe function 240. The ProSe function 240 processes the request andmay authorize one or more V2X services based on the capability list andcredentials provided by the V2X host application 214 (the capabilitylist and credentials of the UE 104, in this case). In some cases, theV2X ProSe function 242 contacts the ITS function 106 to confirm the RSUregistration of the V2X host application 214.

Once authorized, the V2X ProSe function 242 assigns an Application ID toeach associated V2X service. The Application ID may be given to the V2Xhost application 214. Having received authorization from the ITSfunction 106 and registration from the V2X ProSe function 240/V2X ProSefunction 242, the V2X host application 214 connects to the ITS function106 to initialize the V2X services. This may include the establishmentof an EPS bearer, using the obtained IP address, to result in a startedservice that is provided by the ITS function 106 and hosted via the V2Xhost application 214.

The V2X service application 250 in the V2X UE 110 is currentlyregistered with a ProSe function (e.g., ProSe function 240/V2X ProSefunction 242) or may have registered with the ProSe function previously.This registration occurs through the LTE user plane (e.g., LTE-Uuinterface 120). As part of the V2X UE 110 registration, the V2X ProSefunction (e.g., V2X ProSe function 242) verifies whether V2X RSUservices are available at the UE's current location using the locationof registered eNBs providing services and service capabilities supportedby the V2X UE 110. The V2X ProSe function provides a list of availableservices and initial configuration information to the V2X UE 110 (to theV2X service application 250, for example). The configuration informationmay include a mapping of eNB identifiers (e.g., cell identifiers (IDs))to RSU server IP addresses and corresponding service identifiers (e.g.,PSID) within a certain geographical area relevant to the V2X UE 110.

The V2X service application 250 uses the V2X service configurationinformation to discover with the V2X host application 214 in an RSU(e.g., UE 104 as illustrated in FIG. 4, eNB 102 as illustrated in FIG.5, or V2X UE 110 as illustrated in FIG. 1). In some cases, the V2X UE110 uses the eNB that the V2X UE 110 is currently connected to(connected via an LTE-Uu interface 120 or a user plane, for example) asan RSU. The V2X service application 250, which is authorized by the V2XProSe function 242 to utilize the V2X functions, listens toadvertisements sent by devices operating as RSUs and/or eNBs. In oneexample, a device operating as an RSU (e.g., UE 104, eNB 102, or V2X UE110) sends an advertisement in a direct discovery message over anLTE-PC5 interface 130. In another example, an eNB 102 sends anadvertisement in a broadcast message over an LTE-Uu interface 120 (e.g.,through the control plane). For instance, the advertisement is in asystem information block (SIB) of a broadcast message.

The V2X service application 250, which is authorized by the V2X ProSefunction 242 to utilize V2X functions, listens to advertisements sent byan RSU/eNB. The V2X service application 250 is informed of theapplication identity (e.g., Application ID) being used by RSUs based onthe advertisements sent by the RSU/eNB. The application identity is theparameter that is used to identify the particular application thattriggers the DISCOVERY_REQUEST message.

The ProSe host application 214 transmits a direct discovery request(e.g., a DISCOVERY_REQUEST) advertising that the ProSe host application214 is acting as an RSU and/or hosting one or more V2X services.Accordingly, the direct discovery request is used to advertise anavailable service. Using ProSe to facilitate the discovery of and accessto V2X services, V2X services can be geographically targeted (based onthe location/coverage area of the device 210, for example) and V2Xservices may be accessed quickly using low latency ProSe protocols.

Additionally or alternatively, the V2X host application 214 transmits abroadcast message advertising that the V2X host application 214 isacting as an RSU and/or hosting one or more V2X services. The V2X hostapplication 214 may announce its supported V2X services by transmittinga list of V2X service IDs (e.g., PSID) in a System Information Block(SIB). In one embodiment, a new SIB may be created for V2X services,which includes service identifiers, and an indication of whether V2Xservices are provided through the LTE-Uu interface 120 (e.g., userplane) and/or through the LTE-PC5 interface 130. If V2X services areoffered through the LTE-PC5 interface 130, the V2X UE 110 retrieves theadditional LTE-PC5 information from one or more SIBs (e.g., SIB 18 andSIB 19). Alternatively, the V2X service information is included as partof any existing SIBs, such as SIB 18 or SIB 19 for LTE-PC5communications and discovery, respectively.

The V2X service application 250 uses the advertised V2X serviceinformation to decide which RSU (e.g., device 210 with a V2X hostapplication 214) to connect to during initialization or duringhandovers. For example, the V2X service application 250 uses the mappingof services to host devices received from the V2X ProSe function 242,the advertisement included in a direct discovery message, and/or theadvertisement included in a SIB to decide which RSU to connect to duringinitialization or during handovers. If the V2X service application 250decides to connect to a given RSU/eNB, it sends a request to the V2XProSe function 242 to obtain the service configuration information(e.g., PSID, IP address). When the V2X service application 250 leavesthe area of the current RSU, the V2X service application 250 may startmonitoring the ProSe discovery messages (e.g., direct discoverymessages) for another device announcing the RSU functionality.

When the V2X UE 110 performs a handover between eNBs or RSUs, the V2Xservice application 250 uses the RSU to V2X service mapping receivedfrom the V2X ProSe function 242 to identify whether the target device(e.g., eNB) supports the V2X services that the V2X service application250 is currently using. In some cases, the V2X service application 250sends a V2X service handover notification to the current V2X RSUincluding the address of the target device. The current RSU may forwardV2X messages to the target device during the handover procedure. If V2Xservices are not available at the target device, the V2X serviceapplication 250 sends a request to the V2X ProSe function 242 to obtainup to date V2X service configuration information (e.g., PSID, IPaddress) from the V2X ProSe function 242. The configuration informationmay be for RSUs that are located in the nearby area of the V2X UE 110.The V2X ProSe function 242 may periodically send updated configurationinformation to the V2X service application 250 based on the location ofthe V2X UE 110. In one example, the frequency of the updates is based onthe rate of change of the location of the V2X UE 110.

FIG. 5 is a block diagram illustrating one example 400 of a V2X UE 110connecting to an eNB 102 that is enabled to host a V2X service. FIG. 5illustrates that the V2X host application 214 is included in an eNB 102and that the V2X host application 214 in an eNB 102 communicatesdirectly with the V2X service application 250 in the V2X UE 110 via anLTE-PC5 interface 130.

The V2X host application 214 sends a request for authorization tooperate as an RSU to the ITS function/server 106. The ITS server 106 mayrespond with an authorization and may provide specific configurationinformation for RSU operation. The ITS server 106 may be inside theoperator domain or outside the operator domain. In some cases, the ITSserver 106 is part of the V2X ProSe function 242 inside the operatordomain. The configuration information for RSU operation may include aPSID. The V2X host application 214 sends a request for registering itsV2X services with the V2X ProSe function 242 inside the operator domain.The V2X ProSe function 242 responds with an application identity (e.g.,Application ID) to be used by the V2X host application 214 for directdiscovery messages.

The V2X service application 250 performs initial authorization with theV2X ProSe function 242 in order to receive V2X services. The V2X ProSefunction 242 provides a list of available services and initialconfiguration information to the V2X service application 250 and/orProSe application 212. The initial configuration information may includea mapping of eNB identifiers (cell IDs) to RSU server IP addresses andcorresponding service identifiers (e.g., PSID) within a certaingeographical area relevant to the V2X UE 110. The initial configurationinformation may include an application identifier.

The V2X host application 214 (the eNB 102 operating as an RSU) may sendthe RSU configuration information in the broadcast channel. The V2Xservice application 250 used the information received from the V2X ProSefunction 242 to identify whether an eNB is configured as an RSU andwhether that eNB supports the V2X services the V2X UE 110 is currentlyusing. The information received from the V2X ProSe function 242 mayinclude the eNB to V2X service mapping. The information received fromthe V2X ProSe function 242 may also include the application code (e.g.,the Application ID).

When the V2X UE 110 begins a handover procedure and V2X services are notavailable at the target eNB during the handover, the V2X serviceapplication 250 may request up to date V2X service configurationinformation from the V2X ProSe function 242. The V2X ProSe function mayperiodically send updated V2X service configuration information to theV2X service application 250 authorized for V2X services, based on thelocation of the V2X UE 110.

FIG. 6 is one example of a message sequence diagram for the describedsystems and methods. Device 210 sends an RSU authorization request 602to the ITS function 106. The authorization request 602 requests that thedevice 210 operate as an RSU and host one or more V2X services. Upondetermining that the device 210 is authorized to act as an RSU and hostone or more V2X services, the ITS function 106 sends an RSUauthorization response 604 to the device 210 indicating that the device210 is authorized to act as an RSU and host one or more V2X services.Upon receiving authorization, the device 210 sends an RSU registrationrequest 606 to the ProSe function 240. The RSU registration request 606is a request to register one or more V2X services with the ProSefunction 240. The ProSe function 240 sends an RSU registration response608 indicating that the one or more requested V2X services areregistered with the ProSe function 240 and that the device 210 isauthorized to host those registered V2X services within the operatornetwork according to certain configuration parameters.

To verify that the device 210 is authorized to act as an RSU and hostV2X services, the ProSe function 240 may send an RSU registrationnotification 610 to the ITS function 106. With the registration andauthorization completed, the device 210 starts the V2X service 612.Starting the V2X service 612 includes setting up an EPS bearer (using anobtained IP address, for example) so that a V2X service provided by theITS function 106 is hosted and made available by the device 210. Withthe V2X service started and available, the device 210 sends anannouncement 614 (e.g., advertisement) of the V2X service via a directdiscovery message. Additionally or alternatively, the device 210 sends abroadcast with RSU configuration information 616 in a SIB on a broadcastchannel. Prior to the V2X UE 110 being initialized for ProSe V2Xcommunication, the V2X UE 110 may ignore the announcement 614. In oneexample, the V2X UE 110 receives the broadcast with RSU configurationinformation 616 and proceeds with ProSe initiation based on thatbroadcast 616 so that it can access V2X services.

The V2X UE 110 sends an initial authorization 618 to the ProSe function240. The initial authorization 618 is sent via the user plane. The ProSefunction 240 authorizes the V2X UE 110 to utilize ProSe services for V2Xcommunication by sending an authorization to use ProSe for V2X 620. TheProSe function 240 also sends a list of available V2X services 622. Thislist of available services 622 may include a mapping of devices to V2Xservices. Having received authorization to utilize ProSe for V2Xservices, the V2X UE 110 listens for ProSe messages 624.

Again, the device 210 sends an announcement 614 in a direct discoverymessage. The V2X UE 110 receives the announcement 614 and uses V2Xcommunication over an LTE-PC5 interface 628 to access the V2X servicehosted by the device 210. The device 210 enables the V2X communicationvia a V2X service with the ITS function 106.

FIG. 7 is another example of a message sequence diagram for thedescribed systems and methods. As discussed with relation to FIG. 6, theV2X UE 110 performs initial authorization 618 with the ProSe function240, receives authorization to use ProSe for V2X 620, and receives alist of available V2X services 622. Having been configured for V2XProSe, the V2X UE 110 listens for V2X ProSe message 624. The V2X UE 110receives an announcement 614 in a direct discovery message from a sourcedevice 210A and engages in V2X communication with the source device 210Aover the LTE-PC5 interface 628. The source device 210A hosts V2Xcommunication via a V2X service provided by the ITS function 106.

The target device 210B performs authorization and registration to beable to act as an RSU and host one or more V2X services. As discussedwith respect to FIG. 6, the target device 210 sends an RSU authorizationrequest 702 to the ITS function 106 and receives an RSU authorizationresponse 704 from the ITS function 106. The target device 210B thensends an RSU registration request 706 to the ProSe function 240 andreceives an RSU registration response 708 from the ProSe function 240.The ProSe function 240 may send an RSU registration notification 710 tothe ITS function 106. The target device 210B starts the V2X service 712and sends an announcement 714 to the V2X UE 110 in a direct discoverymessage.

The V2X UE 110 may determine to handover from the source device 210A tothe target device 2106. As part of the handover procedure, the V2X UE110 sends a handover notification 716 that identifies the target device210B to the source device 210A. The source device 210A may forward oneor more V2X messages 718 that it receives during the handover procedureto the target device 210B so that the V2X communication with the V2X UE110 can transition smoothly between the source device 210A and thetarget device 210B. With the handover procedure, V2X communication withthe target device 210B may be established over an LTE-PC5 interface 720.The target device 210B, which hosts the V2X service started atcommunication 712, may now host V2X communication via the V2X service722.

FIG. 8 is a flow diagram of a method 800 for V2X communication. Themethod 800 is performed by the V2X UE 110 illustrated in FIGS. 1-7. Inparticular, the method 800 may be performed by the V2X serviceapplication 250 illustrated in FIGS. 2-5. Although the operations ofmethod 800 are illustrated as being performed in a particular order, itis understood that the operations of method 800 may be reordered withoutdeparting from the scope of the method.

At 802, a UE may communicate with a ProSe function of a WWAN over a userplane. At 804, a list of available services is received from the ProSefunction. At 806, a service advertisement is received from a device. Theservice advertisement may be received in a direct discovery message. At808, a service is discovered based on at least one of the received listand the received service advertisement.

The operations of method 800 may be performed by an application specificprocessor, programmable application specific integrated circuit (ASIC),field programmable gate array (FPGA), or the like.

FIG. 9 is a flow diagram of a method 900 for V2X communication. Themethod 900 is performed by the V2X UE 110 illustrated in FIGS. 1-7. Inparticular, the method 900 may be performed by the V2X serviceapplication 250 illustrated in FIGS. 2-5. Although the operations ofmethod 900 are illustrated as being performed in a particular order, itis understood that the operations of method 900 may be reordered withoutdeparting from the scope of the method.

At 902, a UE may communicate with the ProSe function of a WWAN over auser plane. At 904, authorization to utilize ProSe for V2X services isreceived from the ProSe function. At 906, a list of available servicesis received from the ProSe function. At 908, a broadcast message thatincludes V2X service configuration information is received from adevice. The V2X service configuration information may be received in asystem information block (SIB) transmitted on a broadcast channel. At910, a V2X service advertisement is received from the device. The V2Xservice advertisement may be received in a direct discovery message. At912, a service is discovered based on at least one of the received list,the received broadcast message, and the received service advertisement.At 914, a direct interface between the UE and the device is established.At 916, the discovered V2X service is utilized via communications overthe direct interface. The communications may include V2X messagescarried over the LTE-PC5 interface. At 918, V2X messages arecommunicated over the direct interface via the V2X service.

The operations of method 900 may be performed by an application specificprocessor, programmable application specific integrated circuit (ASIC),field programmable gate array (FPGA), or the like.

FIG. 10 is a flow diagram of a method 1000 for enabling V2Xcommunication. The method 1000 is performed by the device 210illustrated in FIGS. 2-7. In particular, the method 1000 may beperformed by the V2X host application 214 illustrated in FIGS. 2-5.Although the operations of method 1000 are illustrated as beingperformed in a particular order, it is understood that the operations ofmethod 1000 may be reordered without departing from the scope of themethod.

At 1002, a registration request is sent to an ITS function. Theregistration request may request authorization for a device to host aV2X service in a cellular network. At 1004, a registration response isreceived from the ITS function. The registration response may authorizethe device to host the V2X service in the cellular network. At 1006, theV2X service is hosted in the cellular network via the ITS function.

The operations of method 1000 may be performed by an applicationspecific processor, programmable application specific integrated circuit(ASIC), field programmable gate array (FPGA), or the like.

FIG. 11 is a flow diagram of a method 1100 for enabling V2Xcommunication. The method 1100 is performed by the device 210illustrated in FIGS. 2-7. In particular, the method 1100 may beperformed by the V2X host application 214 illustrated in FIGS. 2-5.Although the operations of method 1100 are illustrated as beingperformed in a particular order, it is understood that the operations ofmethod 1100 may be reordered without departing from the scope of themethod.

At 1102, an internet protocol (IP) address is obtained for use by avehicle to anything service. At 1104, an intelligent transportationsystem (ITS) function/server is connected to using the obtained IPaddress to initiate the V2X service. At 1106, an authorization requestis sent to the ITS function/server. The authorization request may enablethe ITS function/server to verify that the device is authorized toprovide the V2X service. At 1108, an authorization response is receivedfrom the ITS server. The authorization response may confirm that thedevice is authorized to provide the V2X service. At 1110, a registrationrequest is sent to the ITS function/server. The ITS function/server maybe implemented as part of a proximity services (ProSe) function of acellular network. The registration request may request authorization fora device to host a V2X service in the cellular network. At 1112, aregistration response is received from the ITS function/server. Theregistration response may authorize the device to host the V2X servicein the cellular network. At 1114, the V2X service is hosted in thecellular network via the ITS function. In some cases, the V2X servicemay be hosted using ProSe. At 1116, a V2X service advertisement istransmitted on a PC5 interface. The V2X service advertisement mayindicate that the V2X service is hosted by the device. At 1118, abroadcast message is transmitted on a broadcast channel. The broadcastmessage includes V2X service configuration information. The V2X serviceconfiguration information may be included in a system information block(SIB) of the broadcast message.

The operations of method 1100 may be performed by an applicationspecific processor, programmable application specific integrated circuit(ASIC), field programmable gate array (FPGA), or the like.

FIG. 12 is a flow diagram of a method 1200 for mobility management forV2X communication. The method 1200 is performed by the V2X UE 110illustrated in FIGS. 1-7. In particular, the method 1200 may beperformed by the V2X service application 250 illustrated in FIGS. 2-5.Although the operations of method 1200 are illustrated as beingperformed in a particular order, it is understood that the operations ofmethod 1200 may be reordered without departing from the scope of themethod.

At 1202, a mapping of services to host devices is received from a ProSefunction. At 1204, a service hosted by a first host device is utilizedvia a direct interface between the UE and the first host device. At1206, a service advertisement is received from a host device. Theservice advertisement may be received in a direct discovery message. At1208, a target host device that hosts the service is identified based atleast in part on at least one of the received service advertisement andthe received mapping of services to hosting devices. At 1210, a servicehandover notification is sent to the first host device as part of ahandover procedure. The service handover notification may include anaddress of the identified target host device. At 1212, the servicehosted by the target host device is utilized via a direct interfacebetween the UE and the target host device. The first host device mayforward at least one message for the service to the target host deviceduring the handover procedure. This may ensure that no service messagesare lost during the handover procedure.

The operations of method 1200 may be performed by an applicationspecific processor, programmable application specific integrated circuit(ASIC), field programmable gate array (FPGA), or the like.

FIG. 13 is a block diagram illustrating electronic device circuitry 1300that may be eNB circuitry, UE circuitry, network node circuitry, or someother type of circuitry in accordance with various embodiments. Inembodiments, the electronic device circuitry 1300 may be, or may beincorporated into or otherwise a part of, an eNB, a UE, a mobile station(MS), a BTS, a network node, or some other type of electronic device. Inembodiments, the electronic device circuitry 1300 may include radiotransmit circuitry 1310 and receive circuitry 1312 coupled to controlcircuitry 1314. In embodiments, the transmit circuitry 1310 and/orreceive circuitry 1312 may be elements or modules of transceivercircuitry, as shown. The electronic device circuitry 1300 may be coupledwith one or more plurality of antenna elements 1316 of one or moreantennas. The electronic device circuitry 1300 and/or the components ofthe electronic device circuitry 1300 may be configured to performoperations similar to those described elsewhere in this disclosure.

In embodiments where the electronic device circuitry 1300 is or isincorporated into or otherwise part of a UE, the transmit circuitry 1310can transmit initial authorization communications 618, V2Xcommunications 628, 720, and/or V2X handover notifications 716, as shownin FIGS. 6 and 7. The receive circuitry 1312 can receive initialauthorization communications 618, authorization to use ProSe for V2X620, service advertising announcements 614, broadcasts 616 with SIBconfiguration information, lists of available V2X services 622, and/orV2X communications 628, 720, as shown in FIGS. 6 and 7.

In embodiments where the electronic device circuitry 1300 is an eNB, UE,BTS, and/or a network node, or is incorporated into or is otherwise partof an eNB, UE, BTS, and/or a network node, the transmit circuitry 1310can transmit RSU authorization requests 602, 702, RSU registrationrequests 606, 706, V2X service initiation communications 612, 712,forwarded V2X messages 718, V2X communications over PC5 628, 720, and/orV2X communications 630, 722, as shown in FIGS. 6 and 7. The receivecircuitry 1312 can receive RSU authorization responses 604, 704, RSUregistration responses 608, 708, V2X service initiation communications612, 712, V2X communications over PC5 628, 720, V2X communications viaV2X service 630, 722, and/or forwarded V2X messages 718, as shown inFIGS. 6 and 7.

In certain embodiments, the electronic device circuitry 1300 shown inFIG. 13 is operable to perform one or more methods, such as the methodsshown in FIGS. 8-12.

As used herein, the term “circuitry” may refer to, be part of, orinclude an Application Specific Integrated Circuit (ASIC), an electroniccircuit, a processor (shared, dedicated, or group), and/or memory(shared, dedicated, or group) that execute one or more software orfirmware programs, a combinational logic circuit, and/or other suitablehardware components that provide the described functionality. In someembodiments, the circuitry may be implemented in, or functionsassociated with the circuitry may be implemented by, one or moresoftware or firmware modules. In some embodiments, circuitry may includelogic, at least partially operable in hardware.

Embodiments described herein may be implemented into a system using anysuitably configured hardware and/or software. FIG. 14 is a block diagramillustrating, for one embodiment, example components of a V2X userequipment (UE), UE, mobile station (MS) device, or evolved Node B (eNB)1400. In some embodiments, the UE device 1400 may include applicationcircuitry 1402, baseband circuitry 1404, Radio Frequency (RF) circuitry1406, front-end module (FEM) circuitry 1408, and one or more antennas1410, coupled together at least as shown in FIG. 14.

The application circuitry 1402 may include one or more applicationprocessors. By way of non-limiting example, the application circuitry1402 may include one or more single-core or multi-core processors. Theprocessor(s) may include any combination of general-purpose processorsand dedicated processors (e.g., graphics processors, applicationprocessors, etc.). The processor(s) may be operably coupled and/orinclude memory/storage, and may be configured to execute instructionsstored in the memory/storage to enable various applications and/oroperating systems to run on the system.

By way of non-limiting example, the baseband circuitry 1404 may includeone or more single-core or multi-core processors. The baseband circuitry1404 may include one or more baseband processors and/or control logic.The baseband circuitry 1404 may be configured to process basebandsignals received from a receive signal path of the RF circuitry 1406.The baseband 1404 may also be configured to generate baseband signalsfor a transmit signal path of the RF circuitry 1406. The basebandprocessing circuitry 1404 may interface with the application circuitry1402 for generation and processing of the baseband signals, and forcontrolling operations of the RF circuitry 1406.

By way of non-limiting example, the baseband circuitry 1404 may includeat least one of a second generation (2G) baseband processor 1404A, athird generation (3G) baseband processor 1404B, a fourth generation (4G)baseband processor 1404C, other baseband processor(s) 1404D for otherexisting generations, and generations in development or to be developedin the future (e.g., fifth generation (5G), 6G, etc.). The basebandcircuitry 1404 (e.g., at least one of baseband processors 1404A-1404D)may handle various radio control functions that enable communicationwith one or more radio networks via the RF circuitry 1406. By way ofnon-limiting example, the radio control functions may include signalmodulation/demodulation, encoding/decoding, radio frequency shifting,other functions, and combinations thereof. In some embodiments,modulation/demodulation circuitry of the baseband circuitry 1404 may beprogrammed to perform Fast-Fourier Transform (FFT), precoding,constellation mapping/demapping functions, other functions, andcombinations thereof. In some embodiments, encoding/decoding circuitryof the baseband circuitry 1404 may be programmed to performconvolutions, tail-biting convolutions, turbo, Viterbi, Low DensityParity Check (LDPC) encoder/decoder functions, other functions, andcombinations thereof. Embodiments of modulation/demodulation andencoder/decoder functions are not limited to these examples, and mayinclude other suitable functions.

In some embodiments, the baseband circuitry 1404 may include elements ofa protocol stack. By way of non-limiting example, elements of an evolveduniversal terrestrial radio access network (E-UTRAN) protocol including,for example, physical (PHY), media access control (MAC), radio linkcontrol (RLC), packet data convergence protocol (PDCP), and/or radioresource control (RRC) elements. A central processing unit (CPU) 1404Eof the baseband circuitry 1404 may be programmed to run elements of theprotocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRClayers. In some embodiments, the baseband circuitry 1404 may include oneor more audio digital signal processor(s) (DSP) 1404F. The audio DSP(s)1404F may include elements for compression/decompression and echocancellation. The audio DSP(s) 1404F may also include other suitableprocessing elements.

The baseband circuitry 1404 may further include memory/storage 1404G.The memory/storage 1404G may include data and/or instructions foroperations performed by the processors of the baseband circuitry 1404stored thereon. In some embodiments, the memory/storage 1404G mayinclude any combination of suitable volatile memory and/or non-volatilememory. The memory/storage 1404G may also include any combination ofvarious levels of memory/storage including, but not limited to,read-only memory (ROM) having embedded software instructions (e.g.,firmware), random access memory (e.g., dynamic random access memory(DRAM)), cache, buffers, etc. In some embodiments, the memory/storage1404G may be shared among the various processors or dedicated toparticular processors.

Components of the baseband circuitry 1404 may be suitably combined in asingle chip, a single chipset, or disposed on a same circuit board insome embodiments. In some embodiments, some or all of the constituentcomponents of the baseband circuitry 1404 and the application circuitry1402 may be implemented together, such as, for example, on a system on achip (SOC).

In some embodiments, the baseband circuitry 1404 may provide forcommunication compatible with one or more radio technologies. Forexample, in some embodiments, the baseband circuitry 1404 may supportcommunication with an evolved universal terrestrial radio access network(E-UTRAN) and/or other wireless metropolitan area networks (WMAN), awireless local area network (WLAN), or a wireless personal area network(WPAN). Embodiments in which the baseband circuitry 1404 is configuredto support radio communications of more than one wireless protocol maybe referred to as multi-mode baseband circuitry.

The RF circuitry 1406 may enable communication with wireless networksusing modulated electromagnetic radiation through a non-solid medium. Invarious embodiments, the RF circuitry 1406 may include switches,filters, amplifiers, etc. to facilitate the communication with thewireless network. The RF circuitry 1406 may include a receive signalpath which may include circuitry to down-convert RF signals receivedfrom the FEM circuitry 1408, and provide baseband signals to thebaseband circuitry 1404. The RF circuitry 1406 may also include atransmit signal path which may include circuitry to up-convert basebandsignals provided by the baseband circuitry 1404, and provide RF outputsignals to the FEM circuitry 1408 for transmission.

In some embodiments, the RF circuitry 1406 may include a receive signalpath and a transmit signal path. The receive signal path of the RFcircuitry 1406 may include mixer circuitry 1406A, amplifier circuitry1406B, and filter circuitry 1406C. The transmit signal path of the RFcircuitry 1406 may include filter circuitry 1406C and mixer circuitry1406A. The RF circuitry 1406 may further include synthesizer circuitry1406D configured to synthesize a frequency for use by the mixercircuitry 1406A of the receive signal path and the transmit signal path.In some embodiments, the mixer circuitry 1406A of the receive signalpath may be configured to down-convert RF signals received from the FEMcircuitry 1408 based on the synthesized frequency provided bysynthesizer circuitry 1406D. The amplifier circuitry 1406B may beconfigured to amplify the down-converted signals.

The filter circuitry 1406C may include a low-pass filter (LPF) orband-pass filter (BPF) configured to remove unwanted signals from thedown-converted signals to generate output baseband signals. Outputbaseband signals may be provided to the baseband circuitry 1404 forfurther processing. In some embodiments, the output baseband signals mayinclude zero-frequency baseband signals, although this is not arequirement. In some embodiments, the mixer circuitry 1406A of thereceive signal path may comprise passive mixers, although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 1406A of the transmit signalpath may be configured to up-convert input baseband signals based on thesynthesized frequency provided by the synthesizer circuitry 1406D togenerate RF output signals for the FEM circuitry 1408. The basebandsignals may be provided by the baseband circuitry 1404 and may befiltered by filter circuitry 1406C. The filter circuitry 1406C mayinclude a low-pass filter (LPF), although the scope of the embodimentsis not limited in this respect. In some embodiments, the mixer circuitry1406A of the receive signal path and the mixer circuitry 1406A of thetransmit signal path may include two or more mixers, and may be arrangedfor quadrature downconversion and/or upconversion, respectively. In someembodiments, the mixer circuitry 1406A of the receive signal path andthe mixer circuitry 1406A of the transmit signal path may include two ormore mixers and may be arranged for image rejection (e.g., Hartley imagerejection). In some embodiments, the mixer circuitry 1406A of thereceive signal path and the mixer circuitry 1406A may be arranged fordirect downconversion and/or direct upconversion, respectively. In someembodiments, the mixer circuitry 1406A of the receive signal path andthe mixer circuitry 1406A of the transmit signal path may be configuredfor super-heterodyne operation.

In some embodiments, the output baseband signals and the input basebandsignals may be analog baseband signals, although the scope of theembodiments is not limited in this respect. In some alternateembodiments, the output baseband signals and the input baseband signalsmay be digital baseband signals. In such embodiments, the RF circuitry1406 may include analog-to-digital converter (ADC) and digital-to-analogconverter (DAC) circuitry, and the baseband circuitry 1404 may include adigital baseband interface to communicate with the RF circuitry 1406.

In some dual-mode embodiments, separate radio IC circuitry may beprovided for processing signals for each spectrum, although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 1406D may include one ormore of a fractional-N synthesizer and a fractional N/N+1 synthesizer,although the scope of the embodiments is not limited in this respect asother types of frequency synthesizers may be suitable. For example,synthesizer circuitry 1406D may include a delta-sigma synthesizer, afrequency multiplier, a synthesizer comprising a phase-locked loop witha frequency divider, other synthesizers, and combinations thereof.

The synthesizer circuitry 1406D may be configured to synthesize anoutput frequency for use by the mixer circuitry 1406A of the RFcircuitry 1406 based on a frequency input and a divider control input.In some embodiments, the synthesizer circuitry 1406D may be a fractionalN/N+1 synthesizer.

In some embodiments, frequency input may be provided by a voltagecontrolled oscillator (VCO), although that is not a requirement. Dividercontrol input may be provided by either the baseband circuitry 1404 orthe applications processor 1402 depending on the desired outputfrequency. In some embodiments, a divider control input (e.g., N) may bedetermined from a look-up table based on a channel indicated by theapplications processor 1402.

The synthesizer circuitry 1406D of the RF circuitry 1406 may include adivider, a delay-locked loop (DLL), a multiplexer, and a phaseaccumulator. In some embodiments, the divider may include a dual modulusdivider (DMD), and the phase accumulator may include a digital phaseaccumulator (DPA). In some embodiments, the DMD may be configured todivide the input signal by either N or N+1 (e.g., based on a carry out)to provide a fractional division ratio. In some example embodiments, theDLL may include a set of cascaded, tunable, delay elements, a phasedetector, a charge pump, and a D-type flip-flop. In such embodiments,the delay elements may be configured to break a VCO period into Nd equalpackets of phase, where Nd is the number of delay elements in the delayline. In this way, the DLL may provide negative feedback to help ensurethat the total delay through the delay line is one VCO cycle.

In some embodiments, the synthesizer circuitry 1406D may be configuredto generate a carrier frequency as the output frequency. In someembodiments, the output frequency may be a multiple of the carrierfrequency (e.g., twice the carrier frequency, four times the carrierfrequency, etc.) and used in conjunction with a quadrature generator anddivider circuitry to generate multiple signals at the carrier frequencywith multiple different phases with respect to each other. In someembodiments, the output frequency may be a LO frequency (fLO). In someembodiments, the RF circuitry 1406 may include an IQ/polar converter.

The FEM circuitry 1408 may include a receive signal path which mayinclude circuitry configured to operate on RF signals received from oneor more antennas 1410, amplify the received signals, and provide theamplified versions of the received signals to the RF circuitry 1406 forfurther processing. The FEM circuitry 1408 may also include a transmitsignal path which may include circuitry configured to amplify signalsfor transmission provided by the RF circuitry 1406 for transmission byat least one of the one or more antennas 1410.

In some embodiments, the FEM circuitry 1408 may include a TX/RX switchconfigured to switch between a transmit mode and a receive modeoperation. The FEM circuitry 1408 may include a receive signal path anda transmit signal path. The receive signal path of the FEM circuitry1408 may include a low-noise amplifier (LNA) to amplify received RFsignals and provide the amplified received RF signals as an output(e.g., to the RF circuitry 1406). The transmit signal path of the FEMcircuitry 1408 may include a power amplifier (PA) configured to amplifyinput RF signals (e.g., provided by RF circuitry 1406), and one or morefilters configured to generate RF signals for subsequent transmission(e.g., by one or more of the one or more antennas 1410).

In some embodiments, the MS device 1400 may include additional elementssuch as, for example, memory/storage, a display, a camera, one or moresensors, an input/output (I/O) interface, other elements, andcombinations thereof.

In some embodiments, the MS device 1400 may be configured to perform oneor more processes, techniques, and/or methods as described herein, orportions thereof.

Examples

The following examples pertain to further embodiments.

Example 1 is an apparatus of a device for hosting vehicle to anything(V2X) communication. The device includes one or more processors. The oneor more processors send a registration request to an intelligenttransportation system (ITS) function, the registration request forrequesting authorization for the device to host a V2X service in acellular network, receive a registration response from the ITS function,the registration response authorizing the device to host the V2X servicein the cellular network, and host the V2X service in the cellularnetwork via the ITS function.

Example 2 includes the apparatus of claim 1, where the ITS function isimplemented as part of a proximity services (ProSe) function of thecellular network.

Example 3 includes the apparatus of claim 1, where the ITS function isimplemented as part of a new entity in the cellular network.

Example 4 includes the apparatus of claim 1, where the ITS function isexternal to the cellular network.

Example 5 includes the apparatus of claim 1, where the one or moreprocessors send an authorization request to the ITS function, theauthorization request for verifying that the device is authorized toprovide the V2X service, and receive an authorization response from theITS function, the authorization response confirming that the device isauthorized to provide the V2X service.

Example 6 includes the apparatus of claim 1, where the one or moreprocessors obtain an internet protocol (IP) address for use by the V2Xservice.

Example 7 includes the apparatus of claim 6, where the one or moreprocessors connect to the ITS function using the obtained IP address,initiate the V2X service using the obtained IP address, and host the V2Xservice using the obtained IP address.

Example 8 includes the apparatus of claim 1, where the one or moreprocessors transmit a V2X service advertisement on a PC5 interface, theV2X service advertisement indicating that the V2X service is hosted bythe device.

Example 9 includes the apparatus of claim 8, where the V2X serviceadvertisement is transmitted in broadcast form to all nearby devices.

Example 10 includes the apparatus of claim 8, where the V2X serviceadvertisement is sent in a direct communication message.

Example 11 includes the apparatus of claim 10, where the directcommunication message is a direct discovery message.

Example 12 includes the apparatus of claim 1, where the one or moreprocessors transmit a broadcast message on a broadcast channel, thebroadcast message including V2X service configuration information, wherethe V2X service configuration information is included in a systeminformation block (SIB) of the broadcast message.

Example 13 includes the apparatus of claim 1, where the registrationrequest includes one or more of a service identifier for the V2Xservice, a link layer address for the device, and location informationfor the device.

Example 14 includes the apparatus of claim 1, where the device is atleast one of an evolved Node B (eNB) or a user equipment (UE).

Example 15 includes a user equipment (UE). The UE includes one or moreprocessors. The one or more processors receive a mapping of services tohost devices from a ProSe function, utilize a service hosted by a firsthost device via a direct interface between the UE and the first hostdevice, identify a target host device that hosts the service based atleast in part on the received mapping of services to hosting devices,send a service handover notification to the first host device as part ofa handover procedure, the service handover notification including anaddress of the identified target host device, and utilize the servicehosted by the target host device via a direct interface between the UEand the target host device, where the first host device forwards atleast one message for the service to the target host device during thehandover procedure.

Example 16 includes the UE of claim 15, where the target host device isidentified based on an advertisement received from the target hostdevice, the advertisement indicating that the target host device ishosting the service.

Example 17 includes the UE of claim 16, where the advertisement isreceived in a direct communication message from the target host device.

Example 18 includes the UE of claim 17, where the direct communicationmessage is a direct discovery message.

Example 19 includes the UE of claim 16, where the advertisement isreceived in a system information broadcast from the target host device.

Example 20 includes the UE of claim 19, where the advertisement isincluded in at least one system information block (SIB) of the systeminformation broadcast, and where the at least one SIB is SIB 18 and/orSIB 19.

Example 21 includes the UE of claim 15, where the direct interfacebetween the UE and the first host device and the direct interfacebetween the UE and the target host device are PC5 interfaces.

Example 22 includes the UE of claim 15 or 16, where the service is avehicle to anything (V2X) service.

Example 23 includes a user equipment (UE). The UE includes one or moreprocessors. The one or more processors communicate with a proximityservices (ProSe) function of a wireless wide area network (WWAN) over auser plane, receive a list of available V2X services from the ProSefunction, receive a V2X service advertisement from a device, where theV2X service advertisement is received in a direct discovery message, anddiscover a V2X service based on at least one of the received list andthe received service advertisement.

Example 24 includes the UE of claim 23, where the one or more processorsestablish a direct interface between the UE and the device, and utilizethe discovered V2X service via communications over the direct interface.

Example 25 includes a method for hosting vehicle to anything (V2X)communication. The method includes sending a registration request to anintelligent transportation system (ITS) function, the registrationrequest for requesting authorization for a device to host a V2X servicein a cellular network, receiving a registration response from the ITSfunction, the registration response authorizing the device to host theV2X service in the cellular network, and hosting the V2X service in thecellular network via the ITS function.

Example 26 includes the method of claim 25, where the ITS function isimplemented as part of a proximity services (ProSe) function of thecellular network.

Example 27 includes the method of claim 25, where the ITS function isimplemented as part of a new entity in the cellular network.

Example 28 includes the method of claim 25, where the ITS function isexternal to the cellular network.

Example 29 includes the method of claim 25, where the method includessending an authorization request to the ITS function, the authorizationrequest for verifying that the device is authorized to provide the V2Xservice, and receiving an authorization response from the ITS function,the authorization response confirming that the device is authorized toprovide the V2X service.

Example 30 includes the method of claim 25, where the method includesobtaining an internet protocol (IP) address for use by the V2X service.

Example 31 includes the method of claim 30, where the method includesconnecting to the ITS function using the obtained IP address, initiatingthe V2X service using the obtained IP address, and hosting the V2Xservice using the obtained IP address.

Example 32 includes the method of claim 25, where the method includestransmitting a V2X service advertisement on a PC5 interface, the V2Xservice advertisement indicating that the V2X service is hosted by thedevice.

Example 33 includes the method of claim 32, where the V2X serviceadvertisement is transmitted in broadcast form to all nearby devices.

Example 34 includes the method of claim 32, where the V2X serviceadvertisement is sent in a direct communication message.

Example 35 includes the method of claim 34, where the directcommunication message is a direct discovery message.

Example 36 includes the method of claim 25, where the method includestransmitting a broadcast message on a broadcast channel, the broadcastmessage including V2X service configuration information, where the V2Xservice configuration information is included in a system informationblock (SIB) of the broadcast message.

Example 37 includes the method of claim 25, where the registrationrequest includes one or more of a service identifier for the V2Xservice, a link layer address for the device, and location informationfor the device.

Example 38 includes the method of claim 25, where the device is eitheran evolved Node B (eNB) or a user equipment (UE).

Example 39 includes a method for wireless communication. The methodincludes receiving a mapping of services to host devices from a ProSefunction, utilizing a service hosted by a first host device via a directinterface between the UE and the first host device, identifying a targethost device that hosts the service based at least in part on thereceived mapping of services to hosting devices, sending a servicehandover notification to the first host device as part of a handoverprocedure, the service handover notification including an address of theidentified target host device, and utilizing the service hosted by thetarget host device via a direct interface between the UE and the targethost device, where the first host device forwards at least one messagefor the service to the target host device during the handover procedure.

Example 40 includes the method of claim 39, where the target host deviceis identified based on an advertisement received from the target hostdevice, the advertisement indicating that the target host device ishosting the service.

Example 41 includes the method of claim 40, where the advertisement isreceived in a direct communication message from the target host device.

Example 42 includes the method of claim 41, where the directcommunication message comprises a direct discovery message.

Example 43 includes the method of claim 40, where the advertisement isreceived in a system information broadcast from the target host device.

Example 44 includes the method of claim 43, where the advertisement isincluded in at least one system information block (SIB) of the systeminformation broadcast, and where the at least one SIB is SIB 18 and/orSIB 19.

Example 45 includes the method of claim 39, where the direct interfacebetween the UE and the first host device and the direct interfacebetween the UE and the target host device are PC5 interfaces.

Example 46 includes the method of claim 39 or 40, where the service is avehicle to anything (V2X) service.

Example 47 includes a method for V2X communication. The method includescommunicating with a proximity services (ProSe) function of a wirelesswide area network (WWAN) over a user plane, receiving a list ofavailable V2X services from the ProSe function, receiving a V2X serviceadvertisement from a device, where the V2X service advertisement isreceived in a direct discovery message, and discovering a V2X servicebased on at least one of the received list and the received serviceadvertisement.

Example 48 includes the method of claim 47, where the method includesestablishing a direct interface between the UE and the device, andutilizing the discovered V2X service via communications over the directinterface.

Example 49 includes an apparatus that includes means for performing themethod of any of examples 25-48.

Example 50 includes a machine-readable storage includingmachine-readable instructions, when executed, to implement a method orrealize an apparatus as claimed in any of examples 25-48.

Some of the infrastructure that can be used with embodiments disclosedherein is already available, such as general-purpose computers, mobilephones, computer programming tools and techniques, digital storagemedia, and communications networks. A computing device may include aprocessor such as a microprocessor, microcontroller, logic circuitry, orthe like. The computing device may include a computer-readable storagedevice such as non-volatile memory, static random access memory (RAM),dynamic RAM, read-only memory (ROM), disk, tape, magnetic, optical,flash memory, or other computer-readable storage medium.

Various aspects of certain embodiments may be implemented usinghardware, software, firmware, or a combination thereof. A component ormodule may refer to, be part of, or include an application specificintegrated circuit (ASIC), an electronic circuit, a processor (shared,dedicated, or group), and/or memory (shared, dedicated or group) thatexecute one or more software or firmware programs, a combinational logiccircuit, and/or other suitable components that provide the describedfunctionality. As used herein, a software module or component mayinclude any type of computer instruction or computer executable codelocated within or on a non-transitory computer-readable storage medium.A software module or component may, for instance, comprise one or morephysical or logical blocks of computer instructions, which may beorganized as a routine, program, object, component, data structure,etc., which performs one or more tasks or implements particular abstractdata types.

In certain embodiments, a particular software module or component maycomprise disparate instructions stored in different locations of acomputer-readable storage medium, which together implement the describedfunctionality of the module or component. Indeed, a module or componentmay comprise a single instruction or many instructions, and may bedistributed over several different code segments, among differentprograms, and across several computer-readable storage media. Someembodiments may be practiced in a distributed computing environmentwhere tasks are performed by a remote processing device linked through acommunications network.

Although the foregoing has been described in some detail for purposes ofclarity, it will be apparent that certain changes and modifications maybe made without departing from the principles thereof. It should benoted that there are many alternative ways of implementing both theprocesses and apparatuses described herein. Accordingly, the presentembodiments are to be considered illustrative and not restrictive, andthe disclosure is not to be limited to the details given herein, but maybe modified within the scope and equivalents of the appended claims.

Those having skill in the art will appreciate that many changes may bemade to the details of the above-described embodiments without departingfrom the underlying principles of the disclosure. The scope should,therefore, be determined only by the following claims.

1. An apparatus of a device for hosting vehicle to anything (V2X)communication, the device comprising: one or more processors to: send aregistration request to an intelligent transportation system (ITS)function, the registration request for requesting authorization for thedevice to host a V2X service in a cellular network; receive aregistration response from the ITS function, the registration responseauthorizing the device to host the V2X service in the cellular network;and host the V2X service in the cellular network via the ITS function.2. The apparatus of claim 1, wherein the ITS function is implemented aspart of a proximity services (ProSe) function of the cellular network.3. The apparatus of claim 1, wherein the ITS function is implemented aspart of a new entity in the cellular network.
 4. The apparatus of claim1, wherein the ITS function is external to the cellular network.
 5. Theapparatus of claim 1, wherein the one or more processors are further to:send an authorization request to the ITS function, the authorizationrequest for verifying that the device is authorized to provide the V2Xservice; and receive an authorization response from the ITS function,the authorization response confirming that the device is authorized toprovide the V2X service.
 6. The apparatus of claim 1, wherein the one ormore processors are further to: obtain an internet protocol (IP) addressfor use by the V2X service; connect to the ITS function using theobtained IP address; initiate the V2X service using the obtained IPaddress; and host the V2X service using the obtained IP address.
 7. Theapparatus of claim 1, wherein the one or more processors are further to:transmit a V2X service advertisement on a PC5 interface, the V2X serviceadvertisement indicating that the V2X service is hosted by the device,wherein the V2X service advertisement is transmitted in broadcast formto all nearby devices, and wherein the V2X service advertisement is sentin a direct communication message, wherein the direct communicationmessage comprises a direct discovery message.
 8. The apparatus of claim1, wherein the one or more processors are further to: transmit abroadcast message on a broadcast channel, the broadcast messageincluding V2X service configuration information, wherein the V2X serviceconfiguration information is included in a system information block(SIB) of the broadcast message.
 9. The apparatus of claim 1, wherein theregistration request includes one or more of a service identifier forthe V2X service, a link layer address for the device, and locationinformation for the device.
 10. The apparatus of claim 1, wherein thedevice is at least one of an evolved Node B (eNB) or a user equipment(UE).
 11. A user equipment (UE), comprising: one or more processors to:receive a mapping of services to host devices from a ProSe function;utilize a service hosted by a first host device via a direct interfacebetween the UE and the first host device; identify a target host devicethat hosts the service based at least in part on the received mapping ofservices to hosting devices; send a service handover notification to thefirst host device as part of a handover procedure, the service handovernotification including an address of the identified target host device;and utilize the service hosted by the target host device via a directinterface between the UE and the target host device, wherein the firsthost device forwards at least one message for the service to the targethost device during the handover procedure.
 12. The UE of claim 11,wherein the target host device is identified based on an advertisementreceived from the target host device, the advertisement indicating thatthe target host device is hosting the service, wherein the advertisementis received in a direct communication message from the target hostdevice, and wherein the direct communication message comprises a directdiscovery message.
 13. The UE of claim 11, wherein the advertisement isreceived in a system information broadcast from the target host device,wherein the advertisement is included in at least one system informationblock (SIB) of the system information broadcast, and wherein the atleast one SIB comprises at least one of SIB 18 and SIB
 19. 14. A userequipment (UE), comprising: one or more processors to: communicate witha proximity services (ProSe) function of a wireless wide area network(WWAN) over a user plane; receive a list of available V2X services fromthe ProSe function; receive a V2X service advertisement from a device,wherein the V2X service advertisement is received in a direct discoverymessage; and discover a V2X service based on at least one of thereceived list and the received service advertisement.
 15. The UE ofclaim 14, wherein the one or more processors are further to: establish adirect interface between the UE and the device; and utilize thediscovered V2X service via communications over the direct interface. 16.A method for hosting vehicle to anything (V2X) communication,comprising: sending a registration request to an intelligenttransportation system (ITS) function, the registration request forrequesting authorization for a device to host a V2X service in acellular network; receiving a registration response from the ITSfunction, the registration response authorizing the device to host theV2X service in the cellular network; and hosting the V2X service in thecellular network via the ITS function.
 17. The method of claim 16,wherein the ITS function is implemented as part of a proximity services(ProSe) function of the cellular network.
 18. The method of claim 16,further comprising: sending an authorization request to the ITSfunction, the authorization request for verifying that the device isauthorized to provide the V2X service; and receiving an authorizationresponse from the ITS function, the authorization response confirmingthat the device is authorized to provide the V2X service.
 19. The methodof claim 16, further comprising obtaining an internet protocol (IP)address for use by the V2X service; connecting to the ITS function usingthe obtained IP address; initiating the V2X service using the obtainedIP address; and hosting the V2X service using the obtained IP address.20. The method of claim 16, further comprising: transmitting a V2Xservice advertisement on a PC5 interface, the V2X service advertisementindicating that the V2X service is hosted by the device, wherein the V2Xservice advertisement is transmitted in broadcast form to all nearbydevices, wherein the V2X service advertisement is sent in a directcommunication message, and wherein the direct communication messagecomprises a direct discovery message.
 21. The method of claim 16,further comprising: transmitting a broadcast message on a broadcastchannel, the broadcast message including V2X service configurationinformation, wherein the V2X service configuration information isincluded in a system information block (SIB) of the broadcast message,and wherein the registration request includes one or more of a serviceidentifier for the V2X service, a link layer address for the device, andlocation information for the device.
 22. A method for wirelesscommunication, comprising: receiving a mapping of services to hostdevices from a ProSe function; utilizing a service hosted by a firsthost device via a direct interface between the UE and the first hostdevice; identifying a target host device that hosts the service based atleast in part on the received mapping of services to hosting devices;sending a service handover notification to the first host device as partof a handover procedure, the service handover notification including anaddress of the identified target host device; and utilizing the servicehosted by the target host device via a direct interface between the UEand the target host device, wherein the first host device forwards atleast one message for the service to the target host device during thehandover procedure.
 23. The method of claim 22, wherein the target hostdevice is identified based on an advertisement received from the targethost device, the advertisement indicating that the target host device ishosting the service. 24-25. (canceled)